Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RealNumberQ->RealValuedNumberQ #897

Merged
merged 1 commit into from
Aug 3, 2023
Merged

Conversation

mmatera
Copy link
Contributor

@mmatera mmatera commented Aug 3, 2023

Rename this symbol for compatibility with the last version of WMA

@rocky
Copy link
Member

rocky commented Aug 3, 2023

LGTM - Thanks.

@mmatera mmatera merged commit bb4bfa8 into master Aug 3, 2023
11 checks passed
@mmatera mmatera deleted the realnumberq_to_realvaluednumberq branch August 3, 2023 10:01
@mmatera
Copy link
Contributor Author

mmatera commented Aug 3, 2023

Indeed, it is possible but I am not sure it is a good idea: since our Pattern matching routine is slow and has many flaws, I guess that the best (when is possible) is to use a generic BuiltinRule that dispatches the different cases. When we accomplish the task of fix the pattern matching code, then to revert this would be a relatively easy task.

@rocky
Copy link
Member

rocky commented Aug 3, 2023

Ok, but please don't "fix" the pattern matching routine, especially via a largish PR. Let's discuss in more detail first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants